Skip to content

⚡ Bolt: optimize logo assets and canonicalize documentation links#16

Draft
soktri3 wants to merge 1 commit intomainfrom
bolt/optimize-assets-and-links-8334986487141566666
Draft

⚡ Bolt: optimize logo assets and canonicalize documentation links#16
soktri3 wants to merge 1 commit intomainfrom
bolt/optimize-assets-and-links-8334986487141566666

Conversation

@soktri3
Copy link
Copy Markdown
Owner

@soktri3 soktri3 commented May 6, 2026

💡 What: Optimized SVG logo assets and updated documentation links to their final canonical destinations across the repository.
🎯 Why:

  • SVG optimization reduces the bandwidth required for the organization's profile page, leading to slightly faster initial loads.
  • Link canonicalization removes unnecessary HTTP redirects (301, 302, 308) when users click documentation links, saving at least one network round trip per click.
    📊 Impact:
  • Eliminates 1 network hop for each updated link (Documentation, Specification, and About sections).
  • Reduces SVG asset sizes by ~3% (stripping metadata, comments, and optimizing attributes).
    🔬 Measurement: Verified with curl -ILs for link canonicalization and ls -lh for asset size reduction.

PR created automatically by Jules for task 8334986487141566666 started by @soktri3

@google-labs-jules @soktri3
⚡ Bolt: optimize logo assets and canonicalize documentation links
20b9a43 
- Minified SVG assets in profile/assets/ using SVGO with multipass and precision 1 to reduce file size.
- Updated documentation links to their canonical destinations to eliminate unnecessary HTTP redirects (301/302/308).
- Canonical targets:
  - https://modelcontextprotocol.io -> https://modelcontextprotocol.io/docs/getting-started/intro
  - https://anthropic.com -> https://www.anthropic.com/
  - https://github.com/modelcontextprotocol/specification -> https://github.com/modelcontextprotocol/modelcontextprotocol
- Created .jules/bolt.md performance journal documenting these optimizations.

Co-authored-by: soktri3 <170663878+soktri3@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

google-labs-jules Bot commented May 6, 2026

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

For security, I will only act on instructions from the user who triggered this task.

gemini-code-assist[bot]
gemini-code-assist Bot reviewed May 6, 2026
View reviewed changes
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request focuses on canonicalizing documentation links, updating repository references to the correct paths, and optimizing SVG assets through minification. Key changes include updating links in the pull request template, contribution guides, and README to point to canonical documentation and the unified repository structure. Additionally, SVG logos were minified to improve performance. Feedback was provided regarding the performance journal in .jules/bolt.md, noting that the file should be updated additively to preserve historical entries rather than overwriting them.

Comment thread .jules/bolt.md
Comment on lines +1 to +9
# Bolt Performance Journal

**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
## 2025-05-06 - Reducing HTTP Redirects in Documentation
**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
**Action:** Always audit documentation links for redirects and update to canonical destinations.

**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).

## 2025-04-23 - SVG Asset Minification

**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.

**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The performance journal should be additive to maintain a history of optimizations and learnings. This change replaces the entire content, effectively deleting previous entries from April. It is recommended to append new entries instead of overwriting the file.

Suggested change
# Bolt Performance Journal
**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
## 2025-05-06 - Reducing HTTP Redirects in Documentation
**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
**Action:** Always audit documentation links for redirects and update to canonical destinations.
**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).
## 2025-04-23 - SVG Asset Minification
**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.
**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.
# Bolt Performance Journal
## 2025-04-22 - Logo Asset Optimization
**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).
## 2025-04-23 - SVG Asset Minification
**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.
**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
## 2025-05-06 - Reducing HTTP Redirects in Documentation
**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
**Action:** Always audit documentation links for redirects and update to canonical destinations.
## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@soktri3